Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
contribute:bugs:start [2018/11/17 23:01] – [Bug Reporting abd Fixing] alexxcons | contribute:bugs:start [2024/05/31 23:31] (current) – removed outdated information alexxcons | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOTOC~~ | ||
+ | {{ : | ||
====== Bug Reporting and Fixing====== | ====== Bug Reporting and Fixing====== | ||
- | One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various | + | One of the most useful tasks that we rely on the community for is the testing and reporting of bugs. Since Xfce runs on various |
- | ===== Feature Requests ===== | + | ---- |
- | Although the philosophy of Xfce is to find the correct balance between features and lightweight, | + | ===== Crashes ===== |
- | This right approach for larger changes is to discuss them on the mailing list first. You might think your idea is brilliant, | + | We always try to make the Xfce Desktop Environment as stable as possible; |
- | Afterwards | + | There are a couple of things you can do to help us resolve these issues |
- | Obviously its also nice if you can write a patch that implements the feature, but its not a necessity. | + | ---- |
- | ===== Crashes ===== | + | ==== Search First ==== |
+ | Search the open issues of the project to see if the issue is already known. Also, look through resolved issues because the issue might be fixed already, but has not been released or applied downstream. | ||
- | We always try to make the software as stable as possible, but there is always a possibility a crash or segfault can occur. To problem with crashes is that they are not always reproducible by the developers, this makes it quite often hard to track-down the problem and patch the issue. | + | ---- |
- | Nonetheless there are a couple of things you can do to help resolving them: | + | ==== Report ==== |
- | ==== Search First ==== | ||
- | Search the [[https:// | ||
- | ==== Report ==== | + | When writing your bug report, try to be as descriptive as possible, but avoid verbosity; Mozilla has a nice guide on [[https:// |
If you have not found anything or missed it, report it in the bug tracker. Reports that only say ' | If you have not found anything or missed it, report it in the bug tracker. Reports that only say ' | ||
Line 29: | Line 30: | ||
If the developer cannot reproduce it, he might ask for a // | If the developer cannot reproduce it, he might ask for a // | ||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
==== Backtraces ==== | ==== Backtraces ==== | ||
Line 47: | Line 51: | ||
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
===== Fixing Bugs ===== | ===== Fixing Bugs ===== | ||
Line 52: | Line 59: | ||
Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and attaching a patch file to the reported bug. ( "git format-patch" | Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and attaching a patch file to the reported bug. ( "git format-patch" | ||
- | Not familiar with git? [[contribute/ | + | Not familiar with git? [[contribute/ |
+ | |||
+ | To get started, best read our [[contribute/ | ||
- | After you managed to download the source code, check [[:xfce:building|this manual]] to see how to build a package from it. | + | [[|Back To Top]] |
+ | ---- | ||
+ | [[ :start:|Return to Main Xfce documentation page]] |